Update dev to match mains ci-cd workflow #49
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
note: do not click the update branch button below as that will merge changes from dev into main that we do not want yet - unless we want to make an iterative 0.13.1 release or something similar in which case merging can be performed for that release |
zacharyrobin
approved these changes
Oct 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Updates the ci-cd workflow in this branch to better tag each release accordingly. These updates were also forcefully pushed up into each release branch, which was the easiest way to auto tag each of our releases. Checking docker hub now we have tags from 0.1 to 0.13, latest (main), and experimental (dev). The experimental tag will update once this PR gets merged into dev: https://hub.docker.com/repository/docker/codexrems/pims/tags?page=1&ordering=last_updated
Issue ticket number and Jira link
REMS-491
Checklist before requesting a review
devnot main (the only exception to this is releases fromdevand hotfix branches)Checklist for conducting a review
Workflow
Owner of the Pull Request will be responsible for merge after all requirements are met, including approval from at least one reviewer. Additional changes made after a review will dismiss any approvals and require re-review of the additional updates. Auto merging can be enabled below if additional changes are likely not to be needed. The bot will auto assign reviewers to your Pull Request for you.